ci: allow same-version on the first modelparams release#63
Merged
Conversation
The first release seeds NEXT from package.json (0.0.1), so `npm version 0.0.1` errored with 'Version not changed'. Add --allow-same-version so it's a no-op when the version already matches, while later releases still bump normally.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
💭 Why
The first release ever failed at
npm version: it seedsNEXTfrompackage.json(0.0.1), andnpm version 0.0.1errors withVersion not changedbecause the file already says0.0.1.✨ What changed
--allow-same-versionto the version step (no-op when it already matches; later releases still bump normally).🔧 For operators
On merge, the release re-runs and publishes
modelparams@0.0.1.